NOTES
You cannot delete logs from the browser view.
You can also view the logs from the System Administration view. Choose System Administration from the Selection menu, click Emergency Services Management, and then click CESID Logs.
The logs, starting with the oldest, are overwritten when the maximum file size of 5000 records is reached.
The following table describes scenarios that may generate CESID Logs and/or alarms and what kind of corrective action the system administrator can take.
NOTE: In the table below, a "known" L2 port is a port that is mapped to a CESID in the L2 to CESID Mapping table. An "unknown" L2 port is a port for which there is no L2 to CESID Mapping.
Scenario |
Resulting System Behavior |
Corrective Action |
A newly registered IP device has not been assigned a CESID in the CESID Assignment form and is connecting through an unknown L2 port. |
|
|
A newly registered IP device has been assigned a CESID in the CESID Assignment form and is connecting through an unknown L2 port. |
|
None required. |
A previously known or newly registered device has been assigned a CESID in the CESID Assignment form and is connecting through a known L2 port. |
|
None required. |
A moved device registers at an unknown L2 port. |
|
|
A new or known device registers to a known L2 port, but the CESID for that L2 port does not match the one defined in the CESID Assignment form. |
|
|
A device moves to a known L2 port. |
|
None required. |
A new device registers to a known L2 port but does not have a CESID in the CESID Assignment form. |
|
None required. |